Verviam     Cyber Security     Create Account     Account Profile     Portal Sign In     Configure Users     User Guide    About Verv IAM     Contact Us

Simple Secure Identity Management

Verv IAM


A signed Verv IAM JWT (JSON Web Token) is issued for each endpoint, to be validated prior to request forwarding, secured by PKI rotated keypair.

       
 
Enter 6 digit PIN:     Enter password:  
  Your account requires VPN Sign in. Enter Account ID to verify Verviam VPN connection.
Turn off VPN requirement
To ensure security of authentication, permitted maximum elapsed time since connection to VPN is 4 hours.

Configured REST Services
Review your existing services, endpoint destinations and activity logs. Secure your REST endpoints, manage credentials and configure authorised access. VervIAM authenticates requests at its API Gateway before forwarding them to your configured REST endpoints. For more information, See the Verv IAM Configuration Guide. Verv IAM identity services are further customisable on demand.


     
Choose how credentials are forwarded: encrypted using your account keys, as a signed JWT, or unencrypted where appropriate. Configure endpoint identity, request and response tags, and workflow chains using the options below. Federated identity can be e.g. User ID, Device ID, Client ID, JSON Web Token (JWT). Secrets can be e.g. Password, Client Secret. REST service internet credential is a validated Verv IAM JWT Token with OpenID scopes. See Verv IAM Configuration Guide for more information

Verviam Download Logs as CSV

Business Workflow Configuration
Config Configure Business Workflows:
Configure Workflows:



REST Service Configuration
Config Configure REST Service:
Use only letters, numbers, hyphens, or underscores with no spaces for Endpoint Name. Please input carefully, as the name and description cannot be changed after the Endpoint is created.

 Description :
Connection & Credentials Forwarding
Credentials Forwarding:
  JWT Token RS256 signed with account Private Key (verified with the Public Key). e.g. www.example.com/myApp?JWT=mysignedJWT
  Complete connection string including endpoint URI and credentials e.g.myexampleAPIGateway.com/myapp?query=myquery&secret=mysecret
  SecretID/secretValue and endpoint URI e.g. www.example.com/myApp?userID=encryptedID&password=encryptedPassword



Use the Secrets option for passing credentials in the form of an identifier e.g. UserID and Password, ClientID and Secret Value, TokenID and Token
Forward Endpoint: Verv IAM will forward an unencrypted request as e.g. www.example.com/myApp?userID=myID&password=myPassword. An encrypted request as e.g. www.example.com/myApp?userID=encryptedID&password=encryptedPassword. The encrypted parameters must be decrypted at the endpoint.
          

Use the Connection URI for the destination endpoint connection string. Add optional parameters to complete connection as appropriate
Verv IAM forwards an unencrypted request to an endpoint as e.g. https://www.example.com/connectionURI?query=myquerystring&userID=myuser&pwd=mypass.
Verv IAM forwards an encrypted request as e.g. https://www.example.com/connectionURI?params=myEncryptedOptionalParameters.
Encrypted parameters must be decrypted at the endpoint server. See Verv IAM User Guide
           OK X

   Token expiry (minutes) :     
Add JWS Token Payload (max 5 items). Override token default expiry time of one hour as required. Payload Items can be any custom scopes understood by your application, as well as OAuth 2.0 OpenID Connect required elements. Forward endpoint: Verv IAM will forward a signed JWT request as e.g. https://myServiceEndpointURI?JWT=JWTToken
Credentials Encryption Option:
  Forward my secretID/secret, connection parameters and endpoint tags encrypted with my secret Key, protected by my RSA public/private keypair.
  Forward unencrypted to my application/system. My network connection is secure, and does not require encrypted message content.
Identity & Data Configuration
Identity Data Option:
  Store encrypted identity data for this End User/Endpoint       X

 
    
        
     
      
Endpoint Tags Option:
  Store tags with this End User/Endpoint (maximum 25 tags)        X


       OK Add Tag
OK

Response Tags Option:
  Define response tags for this End User/Endpoint (maximum 25 tags)        X


       OK  Add Tag
OK

Verviam

It is advisable to rotate keys regularly as a strong security measure. This operation cannot be undone!
You must copy all account REST APIs again as the encryption values of your services will be updated.
The new keys may require updated decryption configuration on your system, to decode your endpoint encrypted parameters.
See Verv IAM Configuration Guide for more information on how to use the keys

Keep keys in a safe place. They are only accessible from this page.

Update Rotation Status: Either schedule key rotation or rotate keys now by clicking the update button below. Note: rotating keys means that if you have configured to encrypt your credentials in transit, the decryption key must be updated before decryption at your endpoint URL.

Rotate Account Encryption Keys daily    Note: new JWT tokens are issued every 24 hours
Remove Existing Daily Keys Rotation    Note: JWT tokens will no longer be updated daily

The RSA PublicPrivate Keypair: modulusLength: 2048,
publicKeyEncoding: {type: 'pkcs8', format: 'pem' },
privateKeyEncoding: {type: 'pkcs8', format: 'pem'}.

   

copy Copy Secret Key    
copy Copy Public Key    
copy Copy Private Key    
Verviam

Require Verv IAM VPN to sign in to the account:

  Verv IAM VPN is required to access the account.
  Verv IAM VPN is NOT required to access the account.


**Important**: This updates the Verv IAM VPN configuration. Note when a VPN sign in is required, a VPN client must be installed and configured before you can sign into the account. You cannot configure your VPN unless you have first set up your VPN Client.
Your VPN username is e.g. VerviamAccountID@verviam.directory.com e.g. VP123456789@verviam.directory.com


    copy Copy VPN Password    

Instructions for configuration of VPN to sign in to your Verv IAM Account

Download your VPN configuration file. Configure your VPN Client to use this file to log on to the VPN. Download and install an OpenVPN Client for your device operating system. We recommend AWS OpenVPN Client 3.0.0 or later

VPN Configuration Guide:
    1. Your VPN username is your AccountID@verviam.directory.com e.g. VP1234567890@verviam.directory.com. Copy and save your password.
                VP1234567890@verviam.directory.com
                YourVPNPassword
    2. Download and install AWS OpenVPN Client for your device operating system
    3. Download and save your VerviamVPN.ovpn configuration file. This is the configuration file required by your VPN Client.
    4. Change the Verv IAM VPN config file with the line auth-user-pass "c:\\my-config-directory\\login.txt". Note Windows requires double backslash.
    5. Download and save your VPN client certificate e.g. "c:\\my-config-directory\\client1.domain.tld.crt".
    6. Change the Verv IAM VPN config file with the line --cert. Note Windows requires a double backslash.
    7. Download and save your VPN client key e.g. "c:\\my-config-directory\\client1.domain.tld.key".
    8. Change the Verv IAM VPN config line --key. Note that Windows requires a double backslash.
    9. Configure your downloaded VPN client to use your saved Verv IAM VPN configuration file - VerviamVPN.ovpn
    10. Connect to the VPN. You must be signed into the VPN before you can sign in to the Configure Users, Account Profile and Portal pages.

Verviam